increase compat flexibility to be reasonable#125
Merged
Conversation
Contributor
|
It looks like ArnoldiMethod 4.0 had a breaking change: ArnoldiMethod.jl v0.4.0
|
This was referenced Apr 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on the fact that most people using GXBeam in the FLOW lab right now just manually remove the compat, it's likely that it can be a lot more flexible that it currently is.
Based on the current compat, and the versions of dependencies that appear to work when the compat is removed, I have put together a somewhat more flexible compat so that GXBeam won't be too restrictive to use with other packages.